Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump cdk.version from 1.93.0 to 1.94.1 in /infrastructure #11

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 17, 2021

Bumps cdk.version from 1.93.0 to 1.94.1.
Updates core from 1.93.0 to 1.94.1

Release notes

Sourced from core's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from core's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates apigatewayv2 from 1.93.0 to 1.94.1

Release notes

Sourced from apigatewayv2's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from apigatewayv2's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates lambda from 1.93.0 to 1.94.1

Release notes

Sourced from lambda's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from lambda's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Updates apigatewayv2-integrations from 1.93.0 to 1.94.1

Release notes

Sourced from apigatewayv2-integrations's releases.

v1.94.1

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

v1.94.0

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Changelog

Sourced from apigatewayv2-integrations's changelog.

1.94.1 (2021-03-16)

Bug Fixes

  • s3: Notifications fail to deploy due to incompatible node runtime (#13624) (26bc3d4)

1.94.0 (2021-03-16)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • appmesh: Backend, backend default and Virtual Service client policies structures are being altered
  • appmesh: you must use the backend default interface to define backend defaults in VirtualGateway. The property name also changed from backendsDefaultClientPolicy to backendDefaults
  • appmesh: you must use the backend default interface to define backend defaults in VirtualNode, (the property name also changed from backendsDefaultClientPolicy to backendDefaults), and the Backend class to define a backend
  • appmesh: you can no longer attach a client policy to a VirtualService

Features

Bug Fixes

Commits
  • 60d8f91 chore(release): 1.94.1 (#13625)
  • 3d65124 Error instead of error
  • f3102ed fix changelog heading
  • 818d943 chore(release): 1.94.1
  • 26bc3d4 fix(s3): Notifications fail to deploy due to incompatible node runtime (#13624)
  • 2c1c0eb chore(release): 1.94.0 (#13612)
  • 64dea7c chore(release): 1.94.0
  • 8c6b3eb fix(ec2): Security Groups support all protocols (#13593)
  • 0ec302f chore(region-info): metadata service is in eu-south-1, af-south-1 (#13598)
  • e80a98a feat(ecs-patterns): Add ECS deployment circuit breaker support to higher-leve...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from 000b811 to 9eec372 Compare March 17, 2021 08:45
@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from 9eec372 to f4cf196 Compare March 17, 2021 08:59
@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from f4cf196 to 30be34b Compare March 17, 2021 09:08
@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from 30be34b to b59557e Compare March 17, 2021 09:18
@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 17, 2021

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@pankajagrawal16
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from b59557e to aab7f2d Compare March 17, 2021 09:24
@pankajagrawal16
Copy link
Contributor

@dependabot rebase

Bumps `cdk.version` from 1.93.0 to 1.94.1.

Updates `core` from 1.93.0 to 1.94.1
- [Release notes](https:/aws/aws-cdk/releases)
- [Changelog](https:/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `apigatewayv2` from 1.93.0 to 1.94.1
- [Release notes](https:/aws/aws-cdk/releases)
- [Changelog](https:/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `lambda` from 1.93.0 to 1.94.1
- [Release notes](https:/aws/aws-cdk/releases)
- [Changelog](https:/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Updates `apigatewayv2-integrations` from 1.93.0 to 1.94.1
- [Release notes](https:/aws/aws-cdk/releases)
- [Changelog](https:/aws/aws-cdk/blob/master/CHANGELOG.md)
- [Commits](aws/aws-cdk@v1.93.0...v1.94.1)

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/maven/infrastructure/cdk.version-1.94.1 branch from aab7f2d to 23258e4 Compare March 17, 2021 09:32
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 26, 2021

Superseded by #14.

@dependabot dependabot bot closed this Mar 26, 2021
@dependabot dependabot bot deleted the dependabot/maven/infrastructure/cdk.version-1.94.1 branch March 26, 2021 07:57
devMonkey87 added a commit to devMonkey87/cdk-lambda-packaging-java that referenced this pull request Mar 27, 2023
:add mockito tests to answersService
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment